Repository navigation
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Native consumers can load and edit YAML through the public
core.config.YamlConfigurationfacade without importing Configurate nodes or platform APIs. It supports typed reads, sections and snapshots, classpath defaults for missing files, reload and revision-checked atomic updates. Existing files, including empty files, remain authoritative. Failed reloads and writes preserve the last good snapshot, and updates retain unknown keys.File operations are synchronous and caller-scheduled. Missing-file initialization requires same-directory hard links. If cleanup fails after publication, the new file remains valid and a staged sibling may need cleanup. Same-classloader instances coordinate writes to the same path; cross-process coordination remains the application's responsibility. Case-insensitive reads retain first-key precedence, while writes use exact keys. There is no default overlay or lossless comment round-trip.
Hosted Maven validated head
ea69f3b6with 483 unit tests with one skip and three full-JAR and one shared-JAR artifact check passed. There were zero failures or errors. Build log Local validation also passed 55 focused tests; the packaged shared JAR ran the consumer fixture without platform classes. Downstream mod embedding and native acceptance remain separate.